ebab7d0da53c51438720d60c6e2e467c - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>File Transfer Protocol</title>

</head>

File Transfer Protocol

</h1>

</header>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hatnote{font-style:italic}.mw-parser-output div.hatnote{padding-left:1.6em;margin-bottom:0.5em}.mw-parser-output .hatnote i{font-style:normal}.mw-parser-output .hatnote+link+.hatnote{margin-top:-0.5em}@media print{body.ns-0 .mw-parser-output .hatnote{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div role="note" class="hatnote navigation-not-searchable">"FTP" redirects here. For other uses, see <a href="FTP_(disambiguation)" class="mw-disambig" title="FTP (disambiguation)">FTP (disambiguation)</a>.</div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .infobox-subbox{padding:0;border:none;margin:-3px;width:auto;min-width:100%;font-size:100%;clear:none;float:none;background-color:transparent}.mw-parser-output .infobox-3cols-child{margin:auto}.mw-parser-output .infobox .navbar{font-size:100%}@media screen{html.skin-theme-clientpref-night .mw-parser-output .infobox-full-data:not(.notheme)>div:not(.notheme)[style]{background:#1f1f23!important;color:#f8f9fa}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .infobox-full-data:not(.notheme)>div:not(.notheme)[style]{background:#1f1f23!important;color:#f8f9fa}}@media(min-width:640px){body.skin--responsive .mw-parser-output .infobox-table{display:table!important}body.skin--responsive .mw-parser-output .infobox-table>caption{display:table-caption!important}body.skin--responsive .mw-parser-output .infobox-table>tbody{display:table-row-group}body.skin--responsive .mw-parser-output .infobox-table th,body.skin--responsive .mw-parser-output .infobox-table td{padding-left:inherit;padding-right:inherit}}

/* end https://en.wikipedia.org/ */

</style><table class="infobox vevent" style="width:26em;"><caption class="infobox-title summary">File Transfer Protocol</caption><tbody><tr><td colspan="2" class="infobox-subheader"><a href="Communication_protocol" title="Communication protocol">Communication protocol</a></td></tr><tr><th scope="row" class="infobox-label" style="white-space: nowrap; width:25%;">Purpose</th><td class="infobox-data"><a href="File_transfer" title="File transfer">File transfer</a></td></tr><tr><th scope="row" class="infobox-label" style="white-space: nowrap; width:25%;">Developer(s)</th><td class="infobox-data"><a href="Abhay_Bhushan" title="Abhay Bhushan">Abhay Bhushan</a> for RFC 114</td></tr><tr><th scope="row" class="infobox-label" style="white-space: nowrap; width:25%;">Introduction</th><td class="infobox-data">April 16, 1971 (1971-04-16)</td></tr><tr><th scope="row" class="infobox-label" style="white-space: nowrap; width:25%;"><a href="OSI_model" title="OSI model">OSI layer</a></th><td class="infobox-data"><a href="Application_layer" title="Application layer">Application layer</a></td></tr><tr><th scope="row" class="infobox-label" style="white-space: nowrap; width:25%;"><a href="Port_(computer_networking)" title="Port (computer networking)">Port(s)</a></th><td class="infobox-data">21 for control, 20 for data transfer</td></tr><tr><th scope="row" class="infobox-label" style="white-space: nowrap; width:25%;"><a href="Request_for_Comments" title="Request for Comments">RFC(s)</a></th><td class="infobox-data">RFC 959</td></tr></tbody></table>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hlist dl,.mw-parser-output .hlist ol,.mw-parser-output .hlist ul{margin:0;padding:0}.mw-parser-output .hlist dd,.mw-parser-output .hlist dt,.mw-parser-output .hlist li{margin:0;display:inline}.mw-parser-output .hlist.inline,.mw-parser-output .hlist.inline dl,.mw-parser-output .hlist.inline ol,.mw-parser-output .hlist.inline ul,.mw-parser-output .hlist dl dl,.mw-parser-output .hlist dl ol,.mw-parser-output .hlist dl ul,.mw-parser-output .hlist ol dl,.mw-parser-output .hlist ol ol,.mw-parser-output .hlist ol ul,.mw-parser-output .hlist ul dl,.mw-parser-output .hlist ul ol,.mw-parser-output .hlist ul ul{display:inline}.mw-parser-output .hlist .mw-empty-li{display:none}.mw-parser-output .hlist dt::after{content:": "}.mw-parser-output .hlist dd::after,.mw-parser-output .hlist li::after{content:" · ";font-weight:bold}.mw-parser-output .hlist dd:last-child::after,.mw-parser-output .hlist dt:last-child::after,.mw-parser-output .hlist li:last-child::after{content:none}.mw-parser-output .hlist dd dd:first-child::before,.mw-parser-output .hlist dd dt:first-child::before,.mw-parser-output .hlist dd li:first-child::before,.mw-parser-output .hlist dt dd:first-child::before,.mw-parser-output .hlist dt dt:first-child::before,.mw-parser-output .hlist dt li:first-child::before,.mw-parser-output .hlist li dd:first-child::before,.mw-parser-output .hlist li dt:first-child::before,.mw-parser-output .hlist li li:first-child::before{content:" (";font-weight:normal}.mw-parser-output .hlist dd dd:last-child::after,.mw-parser-output .hlist dd dt:last-child::after,.mw-parser-output .hlist dd li:last-child::after,.mw-parser-output .hlist dt dd:last-child::after,.mw-parser-output .hlist dt dt:last-child::after,.mw-parser-output .hlist dt li:last-child::after,.mw-parser-output .hlist li dd:last-child::after,.mw-parser-output .hlist li dt:last-child::after,.mw-parser-output .hlist li li:last-child::after{content:")";font-weight:normal}.mw-parser-output .hlist ol{counter-reset:listitem}.mw-parser-output .hlist ol>li{counter-increment:listitem}.mw-parser-output .hlist ol>li::before{content:" "counter(listitem)"\a0 "}.mw-parser-output .hlist dd ol>li:first-child::before,.mw-parser-output .hlist dt ol>li:first-child::before,.mw-parser-output .hlist li ol>li:first-child::before{content:" ("counter(listitem)"\a0 "}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1246091330">

/* start https://en.wikipedia.org/ */

.mw-parser-output .sidebar{width:22em;float:right;clear:right;margin:0.5em 0 1em 1em;background:var(--background-color-neutral-subtle,#f8f9fa);border:1px solid var(--border-color-base,#a2a9b1);padding:0.2em;text-align:center;line-height:1.4em;font-size:88%;border-collapse:collapse;display:table}body.skin-minerva .mw-parser-output .sidebar{display:table!important;float:right!important;margin:0.5em 0 1em 1em!important}.mw-parser-output .sidebar-subgroup{width:100%;margin:0;border-spacing:0}.mw-parser-output .sidebar-left{float:left;clear:left;margin:0.5em 1em 1em 0}.mw-parser-output .sidebar-none{float:none;clear:both;margin:0.5em 1em 1em 0}.mw-parser-output .sidebar-outer-title{padding:0 0.4em 0.2em;font-size:125%;line-height:1.2em;font-weight:bold}.mw-parser-output .sidebar-top-image{padding:0.4em}.mw-parser-output .sidebar-top-caption,.mw-parser-output .sidebar-pretitle-with-top-image,.mw-parser-output .sidebar-caption{padding:0.2em 0.4em 0;line-height:1.2em}.mw-parser-output .sidebar-pretitle{padding:0.4em 0.4em 0;line-height:1.2em}.mw-parser-output .sidebar-title,.mw-parser-output .sidebar-title-with-pretitle{padding:0.2em 0.8em;font-size:145%;line-height:1.2em}.mw-parser-output .sidebar-title-with-pretitle{padding:0.1em 0.4em}.mw-parser-output .sidebar-image{padding:0.2em 0.4em 0.4em}.mw-parser-output .sidebar-heading{padding:0.1em 0.4em}.mw-parser-output .sidebar-content{padding:0 0.5em 0.4em}.mw-parser-output .sidebar-content-with-subgroup{padding:0.1em 0.4em 0.2em}.mw-parser-output .sidebar-above,.mw-parser-output .sidebar-below{padding:0.3em 0.8em;font-weight:bold}.mw-parser-output .sidebar-collapse .sidebar-above,.mw-parser-output .sidebar-collapse .sidebar-below{border-top:1px solid #aaa;border-bottom:1px solid #aaa}.mw-parser-output .sidebar-navbar{text-align:right;font-size:115%;padding:0 0.4em 0.4em}.mw-parser-output .sidebar-list-title{padding:0 0.4em;text-align:left;font-weight:bold;line-height:1.6em;font-size:105%}.mw-parser-output .sidebar-list-title-c{padding:0 0.4em;text-align:center;margin:0 3.3em}@media(max-width:640px){body.mediawiki .mw-parser-output .sidebar{width:100%!important;clear:both;float:none!important;margin-left:0!important;margin-right:0!important}}body.skin--responsive .mw-parser-output .sidebar a>img{max-width:none!important}@media screen{html.skin-theme-clientpref-night .mw-parser-output .sidebar:not(.notheme) .sidebar-list-title,html.skin-theme-clientpref-night .mw-parser-output .sidebar:not(.notheme) .sidebar-title-with-pretitle{background:transparent!important}html.skin-theme-clientpref-night .mw-parser-output .sidebar:not(.notheme) .sidebar-title-with-pretitle a{color:var(--color-progressive)!important}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .sidebar:not(.notheme) .sidebar-list-title,html.skin-theme-clientpref-os .mw-parser-output .sidebar:not(.notheme) .sidebar-title-with-pretitle{background:transparent!important}html.skin-theme-clientpref-os .mw-parser-output .sidebar:not(.notheme) .sidebar-title-with-pretitle a{color:var(--color-progressive)!important}}@media print{body.ns-0 .mw-parser-output .sidebar{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><table class="sidebar nomobile nowraplinks hlist"><tbody><tr><th class="sidebar-title"><a href="Internet_protocol_suite" title="Internet protocol suite">Internet protocol suite</a></th></tr><tr><th class="sidebar-heading">

<a href="Application_layer" title="Application layer">Application layer</a></th></tr><tr><td class="sidebar-content">

<li><a href="HTTPS" title="HTTPS">HTTPS</a></li>

<li><a href="Telnet" title="Telnet">Telnet</a></li>

</tr><tr><th class="sidebar-heading">

<a href="Transport_layer" title="Transport layer">Transport layer</a></th></tr><tr><td class="sidebar-content">

</tr><tr><th class="sidebar-heading">

<a href="Internet_layer" title="Internet layer">Internet layer</a></th></tr><tr><td class="sidebar-content">

<li><a href="IPsec" title="IPsec">IPsec</a></li>

</tr><tr><th class="sidebar-heading">

<a href="Link_layer" title="Link layer">Link layer</a></th></tr><tr><td class="sidebar-content">

<li><a href="Tunneling_protocol" title="Tunneling protocol">Tunnels</a></li>

</tr><tr><td class="sidebar-navbar"><style data-mw-deduplicate="TemplateStyles:r1239400231">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbar{display:inline;font-size:88%;font-weight:normal}.mw-parser-output .navbar-collapse{float:left;text-align:left}.mw-parser-output .navbar-boxtext{word-spacing:0}.mw-parser-output .navbar ul{display:inline-block;white-space:nowrap;line-height:inherit}.mw-parser-output .navbar-brackets::before{margin-right:-0.125em;content:"[ "}.mw-parser-output .navbar-brackets::after{margin-left:-0.125em;content:" ]"}.mw-parser-output .navbar li{word-spacing:-0.125em}.mw-parser-output .navbar a>span,.mw-parser-output .navbar a>abbr{text-decoration:inherit}.mw-parser-output .navbar-mini abbr{font-variant:small-caps;border-bottom:none;text-decoration:none;cursor:inherit}.mw-parser-output .navbar-ct-full{font-size:114%;margin:0 7em}.mw-parser-output .navbar-ct-mini{font-size:114%;margin:0 4em}html.skin-theme-clientpref-night .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}@media(prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}}@media print{.mw-parser-output .navbar{display:none!important}}

/* end https://en.wikipedia.org/ */

</style></td></tr></tbody></table>

<td style="background: #ccf; text-align: center;">Internet history timeline

</td></tr>

<tr>

<td>

Early research and development:

<ul><li>1960–1962: <a href="J._C._R._Licklider" title="J. C. R. Licklider">J. C. R. Licklider</a> networking ideas</li>

<li>1960–1964: <a href="RAND" class="mw-redirect" title="RAND">RAND</a> networking concepts developed</li>

<li>1962–1964: <a href="DARPA" title="DARPA">ARPA</a> networking ideas</li>

<li>1965 (1965): <a href="NPL_network" title="NPL network">NPL network</a> concepts conceived</li>

<li>1966 (1966): <a href="Merit_Network" title="Merit Network">Merit Network</a> founded</li>

<li>1967 (1967): <a href="ARPANET" title="ARPANET">ARPANET</a> planning begins</li>

<li>1967 (1967): <a href="Symposium_on_Operating_Systems_Principles" title="Symposium on Operating Systems Principles">Symposium on Operating Systems Principles</a></li>

<li>1969 (1969): NPL followed by the ARPANET carry their first packets</li>

<li>1970 (1970): <a href="InterNIC#History" title="InterNIC">Network Information Center</a> (NIC)</li>

<li>1971 (1971): <a href="Tymnet" title="Tymnet">Tymnet</a> switched-circuit network</li>

<li>1972 (1972): Merit Network's packet-switched network operational</li>

<li>1972 (1972): <a href="Internet_Assigned_Numbers_Authority" title="Internet Assigned Numbers Authority">Internet Assigned Numbers Authority</a> (IANA) established</li>

<li>1973 (1973): <a href="CYCLADES" title="CYCLADES">CYCLADES</a> network demonstrated</li>

<li>1973 (1973): <a href="PARC_Universal_Packet" title="PARC Universal Packet">PARC Universal Packet</a> development begins</li>

<li>1974 (1974): <a href="Transmission_Control_Program" class="mw-redirect" title="Transmission Control Program">Transmission Control Program</a> specification published</li>

<li>1975 (1975): <a href="Telenet" title="Telenet">Telenet</a> commercial packet-switched network</li>

<li>1976 (1976): <a href="X.25" title="X.25">X.25</a> protocol approved and deployed on <a href="Public_data_network" title="Public data network">public data networks</a></li>

<li>1978 (1978): <a href="Minitel" title="Minitel">Minitel</a> introduced</li>

<li>1979 (1979): <a href="Internet_Architecture_Board" title="Internet Architecture Board">Internet Activities Board</a> (IAB)</li>

<li>1980 (1980): <a href="Usenet" title="Usenet">USENET</a> news using <a href="UUCP" title="UUCP">UUCP</a></li>

<li>1980 (1980): <a href="Ethernet" title="Ethernet">Ethernet</a> standard introduced</li>

<li>1981 (1981): <a href="BITNET" title="BITNET">BITNET</a> established</li></ul>

Merging the networks and creating the Internet:

<ul><li>1981 (1981): <a href="CSNET" title="CSNET">Computer Science Network</a> (CSNET)</li>

<li>1982 (1982): <a href="Internet_protocol_suite" title="Internet protocol suite">TCP/IP</a> protocol suite formalized</li>

<li>1982 (1982): <a href="Simple_Mail_Transfer_Protocol" title="Simple Mail Transfer Protocol">Simple Mail Transfer Protocol</a> (SMTP)</li>

<li>1983 (1983): <a href="Domain_Name_System" title="Domain Name System">Domain Name System</a> (DNS)</li>

<li>1983 (1983): <a href="MILNET" title="MILNET">MILNET</a> split off from ARPANET</li>

<li>1984 (1984): <a href="OSI_model" title="OSI model">OSI Reference Model</a> released</li>

<li>1985 (1985): <a href="Domain_names" class="mw-redirect" title="Domain names">First .COM domain name registered</a></li>

<li>1986 (1986): <a href="National_Science_Foundation_Network" title="National Science Foundation Network">NSFNET</a> with 56 kbit/s links</li>

<li>1986 (1986): <a href="Internet_Engineering_Task_Force" title="Internet Engineering Task Force">Internet Engineering Task Force</a> (IETF)</li>

<li>1987 (1987): <a href="UUNET" title="UUNET">UUNET</a> founded</li>

<li>1988 (1988): <a href="National_Science_Foundation_Network" title="National Science Foundation Network">NSFNET</a> upgraded to 1.5 Mbit/s (T1)</li>

<li>1988 (1988): <a href="Morris_worm" title="Morris worm">Morris worm</a></li>

<li>1988 (1988): Complete <a href="Internet_protocol_suite" title="Internet protocol suite">Internet protocol suite</a></li>

<li>1989 (1989): <a href="Border_Gateway_Protocol" title="Border Gateway Protocol">Border Gateway Protocol</a> (BGP)</li>

<li>1989 (1989): <a href="PSINet" title="PSINet">PSINet</a> founded, allows commercial traffic</li>

<li>1989 (1989): <a href="Federal_Internet_Exchange" title="Federal Internet Exchange">Federal Internet Exchanges (FIX East|FIXes)</a></li>

<li>1990 (1990): <a href="Government_Open_Systems_Interconnection_Profile" title="Government Open Systems Interconnection Profile">GOSIP</a> (without <a href="Internet_protocol_suite" title="Internet protocol suite">TCP/IP</a>)</li>

<li>1990 (1990): ARPANET decommissioned</li>

<li>1990 (1990): <a href="Advanced_Network_and_Services" title="Advanced Network and Services">Advanced Network and Services</a> (ANS)</li>

<li>1991 (1991): <a href="Wide_area_information_server" title="Wide area information server">Wide area information server</a> (WAIS)</li>

<li>1991 (1991): <a href="Gopher_(protocol)" title="Gopher (protocol)">Gopher</a></li>

<li>1991 (1991): <a href="Commercial_Internet_eXchange" title="Commercial Internet eXchange">Commercial Internet eXchange</a> (CIX)</li>

<li>1991 (1991): <a href="Advanced_Network_and_Services" title="Advanced Network and Services">ANS CO+RE</a> allows commercial traffic</li>

<li>1991 (1991): <a href="World_Wide_Web" title="World Wide Web">World Wide Web</a> (WWW)</li>

<li>1992 (1992): <a href="National_Science_Foundation_Network" title="National Science Foundation Network">NSFNET</a> upgraded to 45 Mbit/s (T3)</li>

<li>1992 (1992): <a href="Internet_Society" title="Internet Society">Internet Society</a> (ISOC) established</li>

<li>1993 (1993): <a href="Classless_Inter-Domain_Routing" title="Classless Inter-Domain Routing">Classless Inter-Domain Routing</a> (CIDR)</li>

<li>1993 (1993): <a href="InterNIC" title="InterNIC">InterNIC</a> established</li>

<li>1993 (1993): <a href="AOL" title="AOL">AOL</a> added <a href="Usenet" title="Usenet">USENET</a> access</li>

<li>1993 (1993): <a href="NCSA_Mosaic" title="NCSA Mosaic">Mosaic web browser</a> released</li>

<li>1994 (1994): <a href="Search_engine" title="Search engine">Full text web search engines</a></li>

<li>1994 (1994): <a href="North_American_Network_Operators'_Group" title="North American Network Operators' Group">North American Network Operators' Group</a> (NANOG) established</li></ul>

Commercialization, privatization, broader access leads to the modern Internet:

<ul><li>1995 (1995): New Internet architecture with commercial <a href="Internet_service_provider" title="Internet service provider">ISPs</a> connected at <a href="Network_Access_Point" class="mw-redirect" title="Network Access Point">NAPs</a></li>

<li>1995 (1995): <a href="National_Science_Foundation_Network" title="National Science Foundation Network">NSFNET</a> decommissioned</li>

<li>1995 (1995): <a href="GOSIP" class="mw-redirect" title="GOSIP">GOSIP</a> updated to allow <a href="Internet_protocol_suite" title="Internet protocol suite">TCP/IP</a></li>

<li>1995 (1995): <a href="Very_high-speed_Backbone_Network_Service" title="Very high-speed Backbone Network Service">very high-speed Backbone Network Service (vBNS)</a></li>

<li>1996 (1996): <a href="AOL" title="AOL">AOL</a> changes pricing model from hourly to monthly</li>

<li>1998 (1998): <a href="ICANN" title="ICANN">Internet Corporation for Assigned Names and Numbers (ICANN)</a></li>

<li>1999 (1999): <a href="IEEE_802.11" title="IEEE 802.11">IEEE 802.11b</a> wireless networking</li>

<li>1999 (1999): <a href="Internet2" title="Internet2">Internet2</a>/<a href="Abilene_Network" title="Abilene Network">Abilene Network</a></li>

<li>1999 (1999): <a href="VBNS" class="mw-redirect" title="VBNS">vBNS+</a> allows broader access</li>

<li>2000 (2000): <a href="Dot-com_bubble" title="Dot-com bubble">Dot-com bubble</a> bursts</li>

<li>2001 (2001): <a href="Top-level_domain#Proposed_domains" title="Top-level domain">New top-level domain names activated</a></li>

<li>2001 (2001): <a href="Code_Red_(computer_worm)" title="Code Red (computer worm)">Code Red I</a>, <a href="Code_Red_II" title="Code Red II">Code Red II</a>, and <a href="Nimda" title="Nimda">Nimda</a> worms</li>

<li>2003 (2003): <a href="World_Summit_on_the_Information_Society" title="World Summit on the Information Society">UN World Summit on the Information Society (WSIS) phase I</a></li></ul>

<ul><li>2003 (2003): <a href="National_LambdaRail" title="National LambdaRail">National LambdaRail</a> founded</li>

<li>2004 (2004): <a href="Working_Group_on_Internet_Governance" title="Working Group on Internet Governance">UN Working Group on Internet Governance (WGIG)</a></li>

<li>2005 (2005): <a href="World_Summit_on_the_Information_Society" title="World Summit on the Information Society">UN WSIS phase II</a></li>

<li>2006 (2006): <a href="Internet_Governance_Forum" title="Internet Governance Forum">First meeting of the Internet Governance Forum</a></li>

<li>2010 (2010): <a href="Top-level_domain#Internationalized_country_code_TLDs" title="Top-level domain">First internationalized country code top-level domains</a> registered</li>

<li>2012 (2012): <a href="Generic_top-level_domain#New_top-level_domains" title="Generic top-level domain">ICANN begins accepting applications for new generic top-level domain names</a></li>

<li>2013 (2013): <a href="Montevideo_Statement_on_the_Future_of_Internet_Cooperation" title="Montevideo Statement on the Future of Internet Cooperation">Montevideo Statement on the Future of Internet Cooperation</a></li>

<li>2014 (2014): <a href="NetMundial_Initiative" title="NetMundial Initiative">NetMundial international Internet governance proposal</a></li>

<li>2016 (2016): <a href="ICANN" title="ICANN">ICANN</a> contract with U.S. Dept. of Commerce ends, <a href="Internet_Assigned_Numbers_Authority" title="Internet Assigned Numbers Authority">IANA</a> oversight passes to the global Internet community on October 1st</li></ul>

Examples of Internet services:

<ul><li>1989 (1989): <a href="AOL" title="AOL">AOL</a> dial-up service provider, email, instant messaging, and web browser</li>

<li>1995 (1995): <a href="Amazon_(company)" title="Amazon (company)">Amazon</a> online retailer</li>

<li>1995 (1995): <a href="EBay" title="EBay">eBay</a> online auction and shopping</li>

<li>1995 (1995): <a href="Craigslist" title="Craigslist">Craigslist</a> classified advertisements</li>

<li>1995 (1995): <a href="AltaVista" title="AltaVista">AltaVista</a> search engine</li>

<li>1996 (1996): <a href="Outlook.com" title="Outlook.com">Outlook (formerly Hotmail)</a> free web-based e-mail</li>

<li>1996 (1996): <a href="Baidu" title="Baidu">RankDex</a> search engine</li>

<li>1997 (1997): <a href="Google_Search" title="Google Search">Google Search</a></li>

<li>1997 (1997): <a href="Babel_Fish_(website)" title="Babel Fish (website)">Babel Fish</a> automatic translation</li>

<li>1998 (1998): <a href="Yahoo_Groups" title="Yahoo Groups">Yahoo Groups (formerly Yahoo! Clubs)</a></li>

<li>1998 (1998): <a href="PayPal" title="PayPal">PayPal</a> Internet payment system</li>

<li>1998 (1998): <a href="Rotten_Tomatoes" title="Rotten Tomatoes">Rotten Tomatoes</a> review aggregator</li>

<li>1999 (1999): <a href="2channel" title="2channel">2ch</a> Anonymous textboard</li>

<li>1999 (1999): <a href="I-mode" title="I-mode">i-mode</a> mobile internet service</li>

<li>1999 (1999): <a href="Napster" title="Napster">Napster</a> peer-to-peer file sharing</li>

<li>2000 (2000): <a href="Baidu" title="Baidu">Baidu</a> search engine</li>

<li>2003 (2003): <a href="LinkedIn" title="LinkedIn">LinkedIn</a> business networking</li>

<li>2003 (2003): <a href="Myspace" title="Myspace">Myspace</a> social networking site</li>

<li>2003 (2003): <a href="The_Pirate_Bay" title="The Pirate Bay">The Pirate Bay</a>, <a href="Torrent_file" title="Torrent file">torrent file</a> host</li>

<li>2004 (2004): <a href="Facebook" title="Facebook">Facebook</a> social networking site</li>

<li>2004 (2004): <a href="Podcast" title="Podcast">Podcast</a> media file series</li>

<li>2004 (2004): <a href="Flickr" title="Flickr">Flickr</a> image hosting</li>

<li>2005 (2005): <a href="YouTube" title="YouTube">YouTube</a> video sharing</li>

<li>2005 (2005): <a href="Reddit" title="Reddit">Reddit</a> link voting</li>

<li>2005 (2005): <a href="Google_Earth" title="Google Earth">Google Earth</a> virtual globe</li>

<li>2006 (2006): <a href="Twitter" title="Twitter">Twitter</a> microblogging</li>

<li>2007 (2007): <a href="WikiLeaks" title="WikiLeaks">WikiLeaks</a> anonymous news and information leaks</li>

<li>2007 (2007): <a href="Google_Street_View" title="Google Street View">Google Street View</a></li>

<li>2007 (2007): <a href="Amazon_Kindle" title="Amazon Kindle">Kindle</a>, <a href="E-reader" title="E-reader">e-reader</a> and virtual bookshop</li>

<li>2008 (2008): <a href="Amazon_Elastic_Compute_Cloud" title="Amazon Elastic Compute Cloud">Amazon Elastic Compute Cloud</a> (EC2)</li>

<li>2008 (2008): <a href="Dropbox" title="Dropbox">Dropbox</a> cloud-based file hosting</li>

<li>2008 (2008): <a href="Encyclopedia_of_Life" title="Encyclopedia of Life">Encyclopedia of Life</a>, a collaborative encyclopedia intended to document all living species</li>

<li>2008 (2008): <a href="Spotify" title="Spotify">Spotify</a>, a <a href="Digital_rights_management" title="Digital rights management">DRM-based</a> music streaming service</li>

<li>2009 (2009): <a href="Microsoft_Bing" title="Microsoft Bing">Bing</a> search engine</li>

<li>2009 (2009): <a href="Google_Docs" title="Google Docs">Google Docs</a>, Web-based word processor, spreadsheet, presentation, form, and data storage service</li>

<li>2009 (2009): <a href="Kickstarter" title="Kickstarter">Kickstarter</a>, a <a href="Threshold_pledge_system" title="Threshold pledge system">threshold pledge system</a></li>

<li>2009 (2009): <a href="Bitcoin" title="Bitcoin">Bitcoin</a>, a <a href="Digital_currency" title="Digital currency">digital currency</a></li>

<li>2010 (2010): <a href="Instagram" title="Instagram">Instagram</a>, <a href="Photo_sharing" class="mw-redirect" title="Photo sharing">photo sharing</a> and <a href="Social_networking" class="mw-redirect" title="Social networking">social networking</a></li>

<li>2011 (2011): <a href="Google%2B" title="Google+">Google+</a>, <a href="Social_networking" class="mw-redirect" title="Social networking">social networking</a></li>

<li>2011 (2011): <a href="Snapchat" title="Snapchat">Snapchat</a>, <a href="Photo_sharing" class="mw-redirect" title="Photo sharing">photo sharing</a></li>

<li>2012 (2012): <a href="Coursera" title="Coursera">Coursera</a>, massive open online courses</li>

<li>2016 (2016): <a href="TikTok" title="TikTok">TikTok</a>, <a href="Video_sharing" class="mw-redirect" title="Video sharing">video sharing</a> and <a href="Social_networking" class="mw-redirect" title="Social networking">social networking</a></li></ul>

</td></tr></tbody></table>

The File Transfer Protocol (FTP) is a standard <a href="Communication_protocol" title="Communication protocol">communication protocol</a> used for the transfer of <a href="Computer_file" title="Computer file">computer files</a> from a server to a client on a <a href="Computer_network" title="Computer network">computer network</a>. FTP is built on a client–server model architecture using separate control and data connections between the client and the server.<a href="#cite_note-for-1">[1]</a> FTP users may authenticate themselves with a <a href="Plaintext" title="Plaintext">plain-text</a> sign-in protocol, normally in the form of a username and password, but can connect anonymously if the server is configured to allow it. For secure transmission that protects the username and password, and encrypts the content, FTP is often <a href="#Security">secured</a> with <a href="Transport_Layer_Security" title="Transport Layer Security">SSL/TLS</a> (<a href="FTPS" title="FTPS">FTPS</a>) or replaced with <a href="SSH_File_Transfer_Protocol" title="SSH File Transfer Protocol">SSH File Transfer Protocol</a> (SFTP).

The first FTP client applications were <a href="Command-line_interface" title="Command-line interface">command-line programs</a> developed before <a href="Operating_system" title="Operating system">operating systems</a> had <a href="Graphical_user_interface" title="Graphical user interface">graphical user interfaces</a>, and are still shipped with most <a href="Windows" class="mw-redirect" title="Windows">Windows</a>, <a href="Unix" title="Unix">Unix</a>, and <a href="Linux" title="Linux">Linux</a> operating systems.<a href="#cite_note-tcpip-2">[2]</a><a href="#cite_note-net+-3">[3]</a> Many dedicated FTP <a href="Client_(computing)" title="Client (computing)">clients</a> and automation utilities have since been developed for <a href="Desktop_computer" title="Desktop computer">desktops</a>, servers, mobile devices, and hardware, and FTP has been incorporated into productivity applications such as <a href="HTML_editor" title="HTML editor">HTML editors</a> and <a href="File_managers" class="mw-redirect" title="File managers">file managers</a>.

An FTP client used to be commonly integrated in <a href="Web_browser" title="Web browser">web browsers</a>, where file servers are browsed with the <a href="Uniform_Resource_Identifier" title="Uniform Resource Identifier">URI</a> prefix "<code>ftp:// </code>". In 2021, FTP support was dropped by <a href="Google_Chrome" title="Google Chrome">Google Chrome</a> and <a href="Firefox" title="Firefox">Firefox</a>,<a href="#cite_note-:0-4">[4]</a><a href="#cite_note-chromestatus-5">[5]</a> two major web browser vendors, due to it being superseded by the more secure <a href="SSH_File_Transfer_Protocol" title="SSH File Transfer Protocol">SFTP</a> and <a href="FTPS" title="FTPS">FTPS</a>; although neither of them have implemented the newer protocols.<a href="#cite_note-6">[6]</a><a href="#cite_note-7">[7]</a>

<div class="mw-heading mw-heading2"><h2 id="History_of_FTP_servers">History of FTP servers</h2></div>

The original specification for the File Transfer Protocol was written by <a href="Abhay_Bhushan" title="Abhay Bhushan">Abhay Bhushan</a> and published as <style data-mw-deduplicate="TemplateStyles:r1238218222">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc114">114</a> on 16 April 1971. Until 1980, FTP ran on <a href="Network_Control_Protocol_(ARPANET)" title="Network Control Protocol (ARPANET)">NCP</a>, the predecessor of <a href="Internet_protocol_suite" title="Internet protocol suite">TCP/IP</a>.<a href="#cite_note-tcpip-2">[2]</a> The protocol was later replaced by a TCP/IP version, <a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc765">765</a> (June 1980) and <a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc959">959</a> (October 1985), the current specification. Several proposed standards amend <a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc959">959</a>, for example <a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1579">1579</a> (February 1994) enables Firewall-Friendly FTP (passive mode), <a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc2228">2228</a> (June 1997) proposes security extensions, <a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc2428">2428</a> (September 1998) adds support for <a href="IPv6" title="IPv6">IPv6</a> and defines a new type of passive mode.<a href="#cite_note-clark-8">[8]</a>

<div class="mw-heading mw-heading2"><h2 id="Protocol_overview">Protocol overview</h2></div>

<div class="mw-heading mw-heading3"><h3 id="Communication_and_data_transfer">Communication and data transfer</h3></div>

FTP may run in active or passive mode, which determines how the data connection is established.<a href="#cite_note-slack-9">[9]</a> (This sense of "mode" is different from that of the MODE command in the FTP protocol.)

<ul><li>In active mode, the client starts listening for incoming data connections from the server on port M. It sends the FTP command PORT M to inform the server on which port it is listening. The server then initiates a data channel to the client from its port 20, the FTP server data port.</li>

<li>In situations where the client is behind a <a href="Firewall_(computing)" title="Firewall (computing)">firewall</a> and unable to accept incoming TCP connections, passive mode may be used. In this mode, the client uses the control connection to send a PASV command to the server and then receives a server IP address and server port number from the server,<a href="#cite_note-slack-9">[9]</a> which the client then uses to open a data connection from an arbitrary client port to the server IP address and server port number received.<a href="#cite_note-postel-10">[10]</a></li></ul>

Both modes were updated in September 1998 to support <a href="IPv6" title="IPv6">IPv6</a>. Further changes were introduced to the passive mode at that time, updating it to extended passive mode.<a href="#cite_note-11">[11]</a>

The server responds over the control connection with <a href="List_of_FTP_server_return_codes" title="List of FTP server return codes">three-digit status codes</a> in ASCII with an optional text message. For example, "200" (or "200 OK") means that the last command was successful. The numbers represent the code for the response and the optional text represents a human-readable explanation or request (e.g. <Need account for storing file>).<a href="#cite_note-for-1">[1]</a> An ongoing transfer of file data over the data connection can be aborted using an interrupt message sent over the control connection.

FTP needs two ports (one for sending and one for receiving) because it was originally designed to operate on top of <a href="Network_Control_Protocol_(ARPANET)" title="Network Control Protocol (ARPANET)">Network Control Protocol</a> (NCP), which was a <a href="Simplex_communication" class="mw-redirect" title="Simplex communication">simplex protocol</a> that utilized two <a href="List_of_TCP_and_UDP_port_numbers" title="List of TCP and UDP port numbers">port addresses</a>, establishing two connections, for two-way communications. An odd and an even port were reserved for each <a href="Application_layer" title="Application layer">application layer</a> application or protocol. The standardization of TCP and UDP reduced the need for the use of two simplex ports for each application down to one duplex port,<a href="#cite_note-stevens1994v1-12">[12]</a>: 15 but the FTP protocol was never altered to only use one port, and continued using two for backwards compatibility.

<div class="mw-heading mw-heading3"><h3 id="NAT_and_firewall_traversal">NAT and firewall traversal</h3></div>

FTP normally transfers data by having the server connect back to the client, after the PORT command is sent by the client. This is problematic for both <a href="Network_address_translation" title="Network address translation">NATs</a> and firewalls, which do not allow connections from the Internet towards internal hosts.<a href="#cite_note-ncftp-13">[13]</a> For NATs, an additional complication is that the representation of the IP addresses and port number in the PORT command refer to the internal host's IP address and port, rather than the public IP address and port of the NAT.

There are two approaches to solve this problem. One is that the FTP client and FTP server use the PASV command, which causes the data connection to be established from the FTP client to the server.<a href="#cite_note-ncftp-13">[13]</a> This is widely used by modern FTP clients. Another approach is for the NAT to alter the values of the PORT command, using an <a href="Application-level_gateway" title="Application-level gateway">application-level gateway</a> for this purpose.<a href="#cite_note-ncftp-13">[13]</a>

<div class="mw-heading mw-heading3"><h3 id="Data_types">Data types</h3></div>

While transferring data over the network, five data types are defined:<a href="#cite_note-tcpip-2">[2]</a><a href="#cite_note-net+-3">[3]</a><a href="#cite_note-clark-8">[8]</a>

<ul><li><a href="ASCII" title="ASCII">ASCII</a> (TYPE A): Used for text. Data is converted, if needed, from the sending host's character representation to <a href="Extended_ASCII" title="Extended ASCII">"8-bit ASCII"</a> before transmission, and (again, if necessary) to the receiving host's character representation, including <a href="Newline" title="Newline">newlines</a>. As a consequence, this mode is inappropriate for files that contain data other than ASCII.</li>

<li>Image (TYPE I, commonly called <a href="Binary_data" title="Binary data">Binary</a> mode): The sending machine sends each file <a href="Byte" title="Byte">byte</a> by byte, and the recipient stores the <a href="Bytestream" class="mw-redirect" title="Bytestream">bytestream</a> as it receives it. (Image mode support has been recommended for all implementations of FTP).</li>

<li><a href="EBCDIC" title="EBCDIC">EBCDIC</a> (TYPE E): Used for plain text between hosts using the EBCDIC character set.</li>

<li>Local (TYPE L n): Designed to support file transfer between machines which do not use 8-bit bytes, e.g. <a href="36-bit_computing" title="36-bit computing">36-bit systems</a> such as DEC <a href="PDP-10" title="PDP-10">PDP-10s</a>. For example, "TYPE L 9" would be used to transfer data in 9-bit bytes, or "TYPE L 36" to transfer 36-bit words. Most contemporary FTP clients/servers only support L 8, which is equivalent to I.</li>

<li><a href="Unicode" title="Unicode">Unicode</a> text files using <a href="UTF-8" title="UTF-8">UTF-8</a> (TYPE U): defined in an expired <a href="Internet_Draft" title="Internet Draft">Internet Draft</a><a href="#cite_note-14">[14]</a> which never became an RFC, though it has been implemented by several FTP clients/servers.</li></ul>

Note these data types are commonly called "modes", although ambiguously that word is also used to refer to active-vs-passive communication mode (see above), and the modes set by the FTP protocol MODE command (see below).

For text files (TYPE A and TYPE E), three different format control options are provided, to control how the file would be printed:

<ul><li>Non-print (TYPE A N and TYPE E N) – the file does not contain any carriage control characters intended for a printer</li>

<li><a href="Telnet" title="Telnet">Telnet</a> (TYPE A T and TYPE E T) – the file contains Telnet (or in other words, ASCII C0) carriage control characters (CR, LF, etc)</li>

<li><a href="ASA_carriage_control_characters" title="ASA carriage control characters">ASA</a> (TYPE A A and TYPE E A) – the file contains ASA carriage control characters</li></ul>

These formats were mainly relevant to <a href="Line_printer" title="Line printer">line printers</a>; most contemporary FTP clients/servers only support the default format control of N.

<div class="mw-heading mw-heading3"><h3 id="File_structures">File structures</h3></div>

File organization is specified using the STRU command. The following file structures are defined in section 3.1.1 of RFC959:

<ul><li>F or FILE structure (stream-oriented). Files are viewed as an arbitrary sequence of bytes, characters or words. This is the usual file structure on Unix systems and other systems such as CP/M, MS-DOS and Microsoft Windows. (Section 3.1.1.1)</li>

<li>R or RECORD structure (record-oriented). Files are viewed as divided into records, which may be fixed or variable length. This file organization is common on mainframe and midrange systems, such as MVS, VM/CMS, OS/400 and VMS, which support <a href="Record-oriented_filesystem" title="Record-oriented filesystem">record-oriented filesystems</a>.</li>

<li>P or PAGE structure (page-oriented). Files are divided into pages, which may either contain data or metadata; each page may also have a header giving various attributes. This file structure was specifically designed for <a href="TENEX_(operating_system)" title="TENEX (operating system)">TENEX</a> systems, and is generally not supported on other platforms. RFC1123 section 4.1.2.3 recommends that this structure not be implemented.</li></ul>

Most contemporary FTP clients and servers only support STRU F. STRU R is still in use in mainframe and minicomputer file transfer applications.

<div class="mw-heading mw-heading3"><h3 id="Data_transfer_modes">Data transfer modes</h3></div>

Data transfer can be done in any of three modes:<a href="#cite_note-for-1">[1]</a><a href="#cite_note-tcpip-2">[2]</a>

<ul><li>Stream mode (MODE S): Data is sent as a continuous stream, relieving FTP from doing any processing. Rather, all processing is left up to <a href="Transmission_Control_Protocol" title="Transmission Control Protocol">TCP</a>. No End-of-file indicator is needed, unless the data is divided into <a href="Record_(computer_science)" title="Record (computer science)">records</a>.</li>

<li>Block mode (MODE B): Designed primarily for transferring record-oriented files (STRU R), although can also be used to transfer stream-oriented (STRU F) text files. FTP puts each record (or line) of data into several blocks (block header, byte count, and data field) and then passes it on to TCP.<a href="#cite_note-clark-8">[8]</a></li>

<li>Compressed mode (MODE C): Extends MODE B with data compression using <a href="Run-length_encoding" title="Run-length encoding">run-length encoding</a>.</li></ul>

Most contemporary FTP clients and servers do not implement MODE B or MODE C; FTP clients and servers for mainframe and minicomputer operating systems are the exception to that.

Some FTP software also implements a <a href="DEFLATE" class="mw-redirect" title="DEFLATE">DEFLATE</a>-based compressed mode, sometimes called "Mode Z" after the command that enables it. This mode was described in an <a href="Internet_Draft" title="Internet Draft">Internet Draft</a>, but not standardized.<a href="#cite_note-15">[15]</a>

<a href="GridFTP" title="GridFTP">GridFTP</a> defines additional modes, MODE E<a href="#cite_note-16">[16]</a> and MODE X,<a href="#cite_note-17">[17]</a> as extensions of MODE B.

<div class="mw-heading mw-heading3"><h3 id="Additional_commands">Additional commands</h3></div>

More recent implementations of FTP support the Modify Fact: Modification Time (MFMT) command, which allows a client to adjust that <a href="File_attribute" title="File attribute">file attribute</a> remotely, enabling the preservation of that attribute when uploading files.<a href="#cite_note-18">[18]</a><a href="#cite_note-19">[19]</a>

To retrieve a remote file timestamp, there's MDTM command. Some servers (and clients) support nonstandard syntax of the MDTM command with two arguments, that works the same way as MFMT<a href="#cite_note-20">[20]</a>

<div class="mw-heading mw-heading2"><h2 id="Login">Login</h2></div>

FTP login uses normal username and password scheme for granting access.<a href="#cite_note-tcpip-2">[2]</a> The username is sent to the server using the USER command, and the password is sent using the PASS command.<a href="#cite_note-tcpip-2">[2]</a> This sequence is unencrypted "on the wire", so may be vulnerable to a network <a href="Sniffing_attack" title="Sniffing attack">sniffing attack</a>.<a href="#cite_note-21">[21]</a> If the information provided by the client is accepted by the server, the server will send a greeting to the client and the session will commence.<a href="#cite_note-tcpip-2">[2]</a> If the server supports it, users may log in without providing login credentials, but the same server may authorize only limited access for such sessions.<a href="#cite_note-tcpip-2">[2]</a>

<div class="mw-heading mw-heading3"><h3 id="Anonymous_FTP">Anonymous FTP</h3></div>

A host that provides an FTP service may provide <a href="Anonymity" title="Anonymity">anonymous</a> FTP access.<a href="#cite_note-tcpip-2">[2]</a> Users typically log into the service with an 'anonymous' (lower-case and case-sensitive in some FTP servers) account when prompted for user name. Although users are commonly asked to send their <a href="Email" title="Email">email</a> address instead of a password,<a href="#cite_note-net+-3">[3]</a> no verification is actually performed on the supplied data.<a href="#cite_note-rfc16-22">[22]</a> Many FTP hosts whose purpose is to provide software updates will allow anonymous logins.<a href="#cite_note-net+-3">[3]</a>

<div class="mw-heading mw-heading2"><h2 id="Software_support">Software support</h2></div>

<div class="mw-heading mw-heading3"><h3 id="File_managers">File managers</h3></div>

Many file managers tend to have FTP access implemented, such as <a href="File_Explorer" title="File Explorer">File Explorer</a> (formerly Windows Explorer) on <a href="Microsoft_Windows" title="Microsoft Windows">Microsoft Windows</a>. This client is only recommended for small file transfers from a server, due to limitations compared to dedicated client software.<a href="#cite_note-23">[23]</a> It does not support <a href="SSH_File_Transfer_Protocol" title="SSH File Transfer Protocol">SFTP</a>.<a href="#cite_note-24">[24]</a>

Both the native file managers for <a href="KDE" title="KDE">KDE</a> on Linux (<a href="Dolphin_(file_manager)" title="Dolphin (file manager)">Dolphin</a> and <a href="Konqueror" title="Konqueror">Konqueror</a>) support FTP as well as SFTP.<a href="#cite_note-25">[25]</a><a href="#cite_note-26">[26]</a>

On <a href="Android_(operating_system)" title="Android (operating system)">Android</a>, the My Files file manager on <a href="Samsung_Galaxy" title="Samsung Galaxy">Samsung Galaxy</a> has a built-in FTP and <a href="SSH_File_Transfer_Protocol" title="SSH File Transfer Protocol">SFTP</a> client.<a href="#cite_note-27">[27]</a>

<div class="mw-heading mw-heading3"><h3 id="Web_browser">Web browser</h3></div>

For a long time, most common <a href="Web_browser" title="Web browser">web browsers</a> were able to retrieve files hosted on FTP servers, although not all of them had support for protocol extensions such as <a href="FTPS" title="FTPS">FTPS</a>.<a href="#cite_note-net+-3">[3]</a><a href="#cite_note-matthews-28">[28]</a> When an FTP—rather than an HTTP—<a href="URL" title="URL">URL</a> is supplied, the accessible contents on the remote server are presented in a manner that is similar to that used for other web content.

Google Chrome removed FTP support entirely in Chrome 88, also affecting other <a href="Chromium" title="Chromium">Chromium</a>-based browsers such as <a href="Microsoft_Edge" title="Microsoft Edge">Microsoft Edge</a>.<a href="#cite_note-29">[29]</a> Firefox 88 disabled FTP support by default, with Firefox 90 dropping support entirely.<a href="#cite_note-30">[30]</a><a href="#cite_note-:0-4">[4]</a>

<a href="FireFTP" title="FireFTP">FireFTP</a> is a discontinued browser extension that was designed as a full-featured FTP client to be run within <a href="Firefox" title="Firefox">Firefox</a>, but when Firefox dropped support for FTP the extension developer recommended using <a href="Waterfox" title="Waterfox">Waterfox</a>.<a href="#cite_note-31">[31]</a> Some browsers, such as the text-based <a href="Lynx_(web_browser)" title="Lynx (web browser)">Lynx</a>, still support FTP.<a href="#cite_note-32">[32]</a>

<div class="mw-heading mw-heading4"><h4 id="Syntax">Syntax</h4></div>

FTP URL syntax is described in <a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1738">1738</a>, taking the form: <code>ftp://user:password@host:port/path</code>. Only the host is required.

More details on specifying a username and password may be found in the browsers' documentation (e.g., <a href="Firefox" title="Firefox">Firefox</a><a href="#cite_note-33">[33]</a> and <a href="Internet_Explorer" title="Internet Explorer">Internet Explorer</a><a href="#cite_note-34">[34]</a>). By default, most web browsers use passive (PASV) mode, which more easily traverses end-user firewalls.

Some variation has existed in how different browsers treat path resolution in cases where there is a non-root home directory for a user.<a href="#cite_note-35">[35]</a>

<div class="mw-heading mw-heading3"><h3 id="Download_manager">Download manager</h3></div>

Most common <a href="Download_manager" title="Download manager">download managers</a> can receive files hosted on FTP servers, while some of them also give the interface to retrieve the files hosted on FTP servers. <a href="DownloadStudio" class="mw-redirect" title="DownloadStudio">DownloadStudio</a> allows not only download a file from FTP server but also view the list of files on a FTP server.<a href="#cite_note-36">[36]</a>

<div class="mw-heading mw-heading3"><h3 id="Other">Other</h3></div>

<a href="LibreOffice" title="LibreOffice">LibreOffice</a> declared its FTP support deprecated from 7.4 release, this was later removed in 24.2 release.<a href="#cite_note-37">[37]</a><a href="#cite_note-38">[38]</a> <a href="Apache_OpenOffice" title="Apache OpenOffice">Apache OpenOffice</a>, another descent of OpenOffice.org, is still support FTP.<a href="#cite_note-39">[39]</a><a href="#cite_note-40">[40]</a><a href="#cite_note-41">[41]</a>

<div class="mw-heading mw-heading2"><h2 id="Security">Security</h2></div>

FTP was not designed to be a secure protocol, and has many security weaknesses.<a href="#cite_note-nurdle-42">[42]</a> In May 1999, the authors of <a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc2577">2577</a> listed a vulnerability to the following problems:

<ul><li><a href="Brute-force_attack" title="Brute-force attack">Brute-force attack</a></li>

<li><a href="FTP_bounce_attack" title="FTP bounce attack">FTP bounce attack</a></li>

<li><a href="Packet_capture" class="mw-redirect" title="Packet capture">Packet capture</a></li>

<li>Port stealing (guessing the next open port and usurping a legitimate connection)</li>

<li><a href="Spoofing_attack" title="Spoofing attack">Spoofing attack</a></li>

<li>Username enumeration</li>

FTP does not encrypt its traffic; all transmissions are in clear text, and usernames, passwords, commands and data can be read by anyone able to perform packet capture (<a href="Packet_analyzer" title="Packet analyzer">sniffing</a>) on the network.<a href="#cite_note-tcpip-2">[2]</a><a href="#cite_note-nurdle-42">[42]</a> This problem is common to many of the Internet Protocol specifications (such as <a href="SMTP" class="mw-redirect" title="SMTP">SMTP</a>, <a href="Telnet" title="Telnet">Telnet</a>, <a href="Post_Office_Protocol" title="Post Office Protocol">POP</a> and <a href="Internet_Message_Access_Protocol" title="Internet Message Access Protocol">IMAP</a>) that were designed prior to the creation of encryption mechanisms such as <a href="Transport_Layer_Security" title="Transport Layer Security">TLS</a> or SSL.<a href="#cite_note-clark-8">[8]</a>

Common solutions to this problem include:

<ol><li>Using the secure versions of the insecure protocols, e.g., <a href="FTPS" title="FTPS">FTPS</a> instead of FTP and TelnetS instead of Telnet.</li>

<li>Using a different, more secure protocol that can handle the job, e.g. <a href="SSH_File_Transfer_Protocol" title="SSH File Transfer Protocol">SSH File Transfer Protocol</a> or <a href="Secure_Copy_Protocol" class="mw-redirect" title="Secure Copy Protocol">Secure Copy Protocol</a>.</li>

<li>Using a secure tunnel such as <a href="Secure_Shell" title="Secure Shell">Secure Shell</a> (SSH) or <a href="Virtual_private_network" title="Virtual private network">virtual private network</a> (VPN).</li></ol>

FTP over SSH is the practice of tunneling a normal FTP session over a Secure Shell connection.<a href="#cite_note-nurdle-42">[42]</a> Because FTP uses multiple <a href="Transmission_Control_Protocol" title="Transmission Control Protocol">TCP</a> connections (unusual for a TCP/IP protocol that is still in use), it is particularly difficult to tunnel over SSH. With many SSH clients, attempting to set up a tunnel for the control channel (the initial client-to-server connection on port 21) will protect only that channel; when data is transferred, the FTP software at either end sets up new TCP connections (data channels) and thus have no <a href="Confidentiality" title="Confidentiality">confidentiality</a> or <a href="Integrity_protection" class="mw-redirect" title="Integrity protection">integrity protection</a>.

Otherwise, it is necessary for the SSH client software to have specific knowledge of the FTP protocol, to monitor and rewrite FTP control channel messages and autonomously open new <a href="Packet_forwarding" title="Packet forwarding">packet forwardings</a> for FTP data channels. Software packages that support this mode include:

<ul><li>Tectia ConnectSecure (Win/Linux/Unix)<a href="#cite_note-43">[43]</a> of <a href="SSH_Communications_Security" class="mw-redirect" title="SSH Communications Security">SSH Communications Security</a>'s software suite</li></ul>

FTP over SSH should not be confused with <a href="SSH_File_Transfer_Protocol" title="SSH File Transfer Protocol">SSH File Transfer Protocol</a> (SFTP).

<div class="mw-heading mw-heading2"><h2 id="Derivatives">Derivatives</h2></div>

<div role="note" class="hatnote navigation-not-searchable">Main article: <a href="FTPS" title="FTPS">FTPS</a></div>

Explicit FTPS is an extension to the FTP standard that allows clients to request FTP sessions to be encrypted. This is done by sending the "AUTH TLS" command. The server has the option of allowing or denying connections that do not request TLS. This protocol extension is defined in <a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc4217">4217</a>. Implicit FTPS is an outdated standard for FTP that required the use of a SSL or TLS connection. It was specified to use different ports than plain FTP.

<div class="mw-heading mw-heading3"><h3 id="SSH_File_Transfer_Protocol">SSH File Transfer Protocol</h3></div>

<div role="note" class="hatnote navigation-not-searchable">Main article: <a href="SSH_File_Transfer_Protocol" title="SSH File Transfer Protocol">SSH File Transfer Protocol</a></div>

The SSH file transfer protocol (chronologically the second of the two protocols abbreviated SFTP) transfers files and has a similar command set for users, but uses the <a href="Secure_Shell" title="Secure Shell">Secure Shell</a> protocol (SSH) to transfer files. Unlike FTP, it encrypts both commands and data, preventing passwords and sensitive information from being transmitted openly over the network. It cannot interoperate with FTP software, though some FTP client software offers support for the SSH file transfer protocol as well.

<div class="mw-heading mw-heading3"><h3 id="Trivial_File_Transfer_Protocol">Trivial File Transfer Protocol</h3></div>

<div role="note" class="hatnote navigation-not-searchable">Main article: <a href="Trivial_File_Transfer_Protocol" title="Trivial File Transfer Protocol">Trivial File Transfer Protocol</a></div>

Trivial File Transfer Protocol (TFTP) is a simple, lock-step FTP that allows a client to get a file from or put a file onto a remote host. One of its primary uses is in the early stages of <a href="Network_booting" title="Network booting">booting from a local area network</a>, because TFTP is very simple to implement. TFTP lacks security and most of the advanced features offered by more robust file transfer protocols such as File Transfer Protocol. TFTP was first standardized in 1981 and the current specification for the protocol can be found in <a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1350">1350</a>.

<div class="mw-heading mw-heading3"><h3 id="Simple_File_Transfer_Protocol">Simple File Transfer Protocol</h3></div>

Simple File Transfer Protocol (the first protocol abbreviated SFTP), as defined by <a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc913">913</a>, was proposed as an (unsecured) file transfer protocol with a level of complexity intermediate between TFTP and FTP. It was never widely accepted on the <a href="Internet" title="Internet">Internet</a>, and is now assigned Historic status by the <a href="Internet_Engineering_Task_Force" title="Internet Engineering Task Force">IETF</a>. It runs through port 115, and often receives the initialism of SFTP. It has a command set of 11 commands and support three types of data transmission: <a href="ASCII" title="ASCII">ASCII</a>, <a href="Binary_file" title="Binary file">binary</a> and continuous. For systems with a <a href="Word_size" class="mw-redirect" title="Word size">word size</a> that is a multiple of 8 bits, the implementation of binary and continuous is the same. The protocol also supports login with user ID and password, hierarchical folders and file management (including rename, delete, upload, download, download with overwrite, and download with append).

<div class="mw-heading mw-heading2"><h2 id="FTP_commands">FTP commands</h2></div>

<div role="note" class="hatnote navigation-not-searchable">Main article: <a href="List_of_FTP_commands" title="List of FTP commands">List of FTP commands</a></div>

<div class="mw-heading mw-heading2"><h2 id="FTP_reply_codes">FTP reply codes</h2></div>

<div role="note" class="hatnote navigation-not-searchable">Main article: <a href="List_of_FTP_server_return_codes" title="List of FTP server return codes">List of FTP server return codes</a></div>

Below is a summary of <a href="List_of_FTP_server_return_codes" title="List of FTP server return codes">FTP reply codes</a> that may be returned by an FTP <a href="Server_(computing)" title="Server (computing)">server</a>. These codes have been standardized in <a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc959">959</a> by the IETF. The reply code is a three-digit value. The first digit is used to indicate one of three possible outcomes — success, failure, or to indicate an error or incomplete reply:

<ul><li>2yz – Success reply</li>

<li>4yz or 5yz – Failure reply</li>

<li>1yz or 3yz – Error or Incomplete reply</li></ul>

The second digit defines the kind of error:

<ul><li>x0z – Syntax. These replies refer to syntax errors.</li>

<li>x1z – Information. Replies to requests for information.</li>

<li>x2z – Connections. Replies referring to the control and data connections.</li>

<li>x3z – Authentication and accounting. Replies for the login process and accounting procedures.</li>

<li>x4z – Not defined.</li>

<li>x5z – File system. These replies relay status codes from the server file system.</li></ul>

The third digit of the reply code is used to provide additional detail for each of the categories defined by the second digit.

/* start https://en.wikipedia.org/ */

.mw-parser-output .div-col{margin-top:0.3em;column-width:30em}.mw-parser-output .div-col-small{font-size:90%}.mw-parser-output .div-col-rules{column-rule:1px solid #aaa}.mw-parser-output .div-col dl,.mw-parser-output .div-col ol,.mw-parser-output .div-col ul{margin-top:0}.mw-parser-output .div-col li,.mw-parser-output .div-col dd{page-break-inside:avoid;break-inside:avoid-column}

/* end https://en.wikipedia.org/ */

</style><div class="div-col" style="column-width: 20em;">

<ul><li><a href="Comparison_of_FTP_client_software" title="Comparison of FTP client software">Comparison of FTP client software</a></li>

<li><a href="Comparison_of_FTP_server_software_packages" title="Comparison of FTP server software packages">Comparison of FTP server software packages</a></li>

<li><a href="Comparison_of_file_transfer_protocols" title="Comparison of file transfer protocols">Comparison of file transfer protocols</a></li>

<li><a href="Curl-loader" title="Curl-loader">Curl-loader</a> – FTP/S loading/testing open-source software</li>

<li><a href="File_eXchange_Protocol" title="File eXchange Protocol">File eXchange Protocol</a> (FXP)</li>

<li><a href="File_Service_Protocol" title="File Service Protocol">File Service Protocol</a> (FSP)</li>

<li><a href="FTPFS" title="FTPFS">FTPFS</a></li>

<li><a href="List_of_FTP_commands" title="List of FTP commands">List of FTP commands</a></li>

<li><a href="List_of_FTP_server_return_codes" title="List of FTP server return codes">List of FTP server return codes</a></li>

<li><a href="Managed_File_Transfer" class="mw-redirect" title="Managed File Transfer">Managed File Transfer</a></li>

<li><a href="Shared_file_access" class="mw-redirect" title="Shared file access">Shared file access</a></li>

<li><a href="TCP_Wrapper" class="mw-redirect" title="TCP Wrapper">TCP Wrapper</a></li></ul></div>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist">

<li id="cite_note-for-1">^ <a href="#cite_ref-for_1-0">a</a> <a href="#cite_ref-for_1-1">b</a> <a href="#cite_ref-for_1-2">c</a> <cite id="CITEREFForouzan2000" class="citation book cs1">Forouzan, B.A. (2000). TCP/IP: Protocol Suite (1st ed.). New Delhi, India: Tata McGraw-Hill Publishing Company Limited.</cite>

</li>

<li id="cite_note-tcpip-2">^ <a href="#cite_ref-tcpip_2-0">a</a> <a href="#cite_ref-tcpip_2-1">b</a> <a href="#cite_ref-tcpip_2-2">c</a> <a href="#cite_ref-tcpip_2-3">d</a> <a href="#cite_ref-tcpip_2-4">e</a> <a href="#cite_ref-tcpip_2-5">f</a> <a href="#cite_ref-tcpip_2-6">g</a> <a href="#cite_ref-tcpip_2-7">h</a> <a href="#cite_ref-tcpip_2-8">i</a> <a href="#cite_ref-tcpip_2-9">j</a> <cite id="CITEREFKozierok2005" class="citation web cs1">Kozierok, Charles M. (2005). <a rel="nofollow" class="external text" href="http://www.tcpipguide.com/free/t_FTPOverviewHistoryandStandards.htm">"The TCP/IP Guide v3.0"</a>. Tcpipguide.com.</cite>

</li>

<li id="cite_note-net+-3">^ <a href="#cite_ref-net+_3-0">a</a> <a href="#cite_ref-net+_3-1">b</a> <a href="#cite_ref-net+_3-2">c</a> <a href="#cite_ref-net+_3-3">d</a> <a href="#cite_ref-net+_3-4">e</a> <cite id="CITEREFDean2010" class="citation book cs1">Dean, Tamara (2010). Network+ Guide to Networks. Delmar. pp. 168–171.</cite>

</li>

<li id="cite_note-:0-4">^ <a href="#cite_ref-:0_4-0">a</a> <a href="#cite_ref-:0_4-1">b</a> <cite id="CITEREFVonau2021" class="citation web cs1">Vonau, Manuel (7 July 2021). <a rel="nofollow" class="external text" href="https://www.androidpolice.com/2021/07/14/firefox-90-fully-removes-ftp-support-and-reorganizes-some-settings-apk-download/">"Firefox follows in Chrome's footsteps and drops FTP support (APK Download)"</a>. Android Police. Retrieved 12 July 2021.</cite>

</li>

<li id="cite_note-chromestatus-5"><a href="#cite_ref-chromestatus_5-0">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://chromestatus.com/feature/6246151319715840">"Remove FTP support - Chrome Platform Status"</a>. www.chromestatus.com. Retrieved 2 September 2021.</cite>

</li>

<li id="cite_note-6"><a href="#cite_ref-6">^</a> <cite id="CITEREFby2020" class="citation web cs1">by, Written (23 March 2020). <a rel="nofollow" class="external text" href="https://news.sophos.com/en-us/2020/03/23/firefox-is-dropping-ftp-support/">"Firefox is dropping FTP support"</a>. Sophos News. Retrieved 13 October 2023.</cite>

</li>

<li id="cite_note-7"><a href="#cite_ref-7">^</a> <cite id="CITEREFEdwards2022" class="citation web cs1">Edwards, Benj (14 July 2022). <a rel="nofollow" class="external text" href="https://www.howtogeek.com/744569/chrome-and-firefox-killed-ftp-support-heres-an-easy-alternative/">"Chrome and Firefox Killed FTP Support: Here's an Easy Alternative"</a>. How-To Geek. Retrieved 13 October 2023.</cite>

</li>

<li id="cite_note-clark-8">^ <a href="#cite_ref-clark_8-0">a</a> <a href="#cite_ref-clark_8-1">b</a> <a href="#cite_ref-clark_8-2">c</a> <a href="#cite_ref-clark_8-3">d</a> <cite id="CITEREFClark2003" class="citation book cs1">Clark, M.P. (2003). Data Networks IP and the Internet (1st ed.). West Sussex, England: John Wiley & Sons Ltd.</cite>

</li>

<li id="cite_note-slack-9">^ <a href="#cite_ref-slack_9-0">a</a> <a href="#cite_ref-slack_9-1">b</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://slacksite.com/other/ftp.html">"Active FTP vs. Passive FTP, a Definitive Explanation"</a>. Slacksite.com.</cite>

</li>

<li id="cite_note-postel-10"><a href="#cite_ref-postel_10-0">^</a> <a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc959">959</a> (Standard) File Transfer Protocol (FTP). Postel, J. & Reynolds, J. (October 1985).

</li>

<li id="cite_note-11"><a href="#cite_ref-11">^</a> <a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc2428">2428</a> (Proposed Standard) Extensions for IPv6, NAT, and Extended Passive Mode. Allman, M. & Metz, C. & Ostermann, S. (September 1998).

</li>

<li id="cite_note-stevens1994v1-12"><a href="#cite_ref-stevens1994v1_12-0">^</a> <cite id="CITEREFStevens1994" class="citation book cs1">Stevens, W. Richard (1994). TCP/IP Illustrated Volume I. Vol. 1. Reading, Massachusetts, USA: Addison-Wesley Publishing Company. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>0-201-63346-9</bdi>.</cite>

</li>

<li id="cite_note-ncftp-13">^ <a href="#cite_ref-ncftp_13-0">a</a> <a href="#cite_ref-ncftp_13-1">b</a> <a href="#cite_ref-ncftp_13-2">c</a> <cite id="CITEREFGleason2005" class="citation web cs1">Gleason, Mike (2005). <a rel="nofollow" class="external text" href="https://www.ncftp.com/ncftpd/doc/misc/ftp_and_firewalls.html">"The File Transfer Protocol and Your Firewall/NAT"</a>. Ncftp.com.</cite>

</li>

<li id="cite_note-14"><a href="#cite_ref-14">^</a> <cite id="CITEREFKlensin" class="citation cs1">Klensin, John. <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/draft-klensin-ftpext-typeu-00">FTP TYPE Extension for Internationalized Text</a>. I-D draft-klensin-ftpext-typeu-00. Retrieved 9 June 2020.</cite>

</li>

<li id="cite_note-15"><a href="#cite_ref-15">^</a> <cite id="CITEREFPreston2005" class="citation cs1">Preston, J. (January 2005). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/draft-preston-ftpext-deflate-03">Deflate transmission mode for FTP</a>. <a href="Internet_Engineering_Task_Force" title="Internet Engineering Task Force">IETF</a>. I-D draft-preston-ftpext-deflate-03. Retrieved 27 January 2016.</cite>

</li>

<li id="cite_note-16"><a href="#cite_ref-16">^</a> <cite id="CITEREFAllcock2003" class="citation web cs1">Allcock, W. (April 2003). <a rel="nofollow" class="external text" href="https://ogf.org/documents/GFD.20.pdf">"GridFTP: Protocol Extensions to FTP for the Grid"</a> (PDF).</cite>

</li>

<li id="cite_note-17"><a href="#cite_ref-17">^</a> <cite id="CITEREFMandrichenko2005" class="citation web cs1">Mandrichenko, I. (4 May 2005). <a rel="nofollow" class="external text" href="https://ogf.org/documents/GFD.47.pdf">"GridFTP v2 Protocol Description"</a> (PDF).</cite>

</li>

<li id="cite_note-18"><a href="#cite_ref-18">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://support.solarwinds.com/SuccessCenter/s/article/MFMT-FTP-command">"MFMT FTP command"</a>. support.solarwinds.com. 11 October 2018.</cite>

</li>

<li id="cite_note-19"><a href="#cite_ref-19">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.serv-u.com/resources/tutorial/dsiz-mfct-mfmt-avbl-pass-xpwd-xmkd-ftp-command">"FTP Commands: DSIZ, MFCT, MFMT, AVBL, PASS, XPWD, XMKD | Serv-U"</a>. www.serv-u.com.</cite>

</li>

<li id="cite_note-20"><a href="#cite_ref-20">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://support.solarwinds.com/SuccessCenter/s/article/MDTM-FTP-command">"MDTM FTP command"</a>. support.solarwinds.com. 11 October 2018.</cite>

</li>

<li id="cite_note-21"><a href="#cite_ref-21">^</a> <cite id="CITEREFPrince2012" class="citation web cs1">Prince, Brian (24 January 2012). <a rel="nofollow" class="external text" href="https://www.securityweek.com/should-organizations-retire-ftp-security/">"Should Organizations Retire FTP for Security?"</a>. Security Week. Retrieved 14 September 2017.</cite>

</li>

<li id="cite_note-rfc16-22"><a href="#cite_ref-rfc16_22-0">^</a> <a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1635">1635</a> (Informational) How to Use Anonymous FTP. P. & Emtage, A. & Marine, A. (May 1994).

</li>

<li id="cite_note-23"><a href="#cite_ref-23">^</a> <a rel="nofollow" class="external text" href="https://helpdesk.egnyte.com/hc/en-us/articles/201637914-FTP-Access-through-Windows-Explorer">FTP Access through Windows Explorer</a>

</li>

<li id="cite_note-24"><a href="#cite_ref-24">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://fpl.cs.depaul.edu/jriely/373/lectures/class-01-014.html">"CSC373/406: SSH [2011/03/27-29]"</a>. fpl.cs.depaul.edu. Retrieved 13 October 2023.</cite>

</li>

<li id="cite_note-25"><a href="#cite_ref-25">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://docs.kde.org/stable5/en/konqueror/konqueror/ftp.html">"FTP"</a>. docs.kde.org. Retrieved 13 October 2023.</cite>

</li>

<li id="cite_note-26"><a href="#cite_ref-26">^</a> <cite id="CITEREFCohen2023" class="citation web cs1">Cohen, Brent (26 July 2023). <a rel="nofollow" class="external text" href="https://devicetests.com/connect-ftp-sftp-dolphin">"How To Connect to FTP/SFTP in Dolphin | DeviceTests"</a>. Retrieved 13 October 2023.</cite>

</li>

<li id="cite_note-27"><a href="#cite_ref-27">^</a> <cite id="CITEREFStaff2022" class="citation web cs1">Staff, Moyens (28 February 2022). <a rel="nofollow" class="external text" href="https://uk.moyens.net/android/samsung-my-files-vs-google-files-which-file-manager-is-better-on-galaxy-phones/">"Samsung My Files vs Google Files: Which File Manager is Better on Galaxy Phones"</a>. Moyens I/O. Retrieved 13 October 2023.</cite>

</li>

<li id="cite_note-matthews-28"><a href="#cite_ref-matthews_28-0">^</a> <cite id="CITEREFMatthews2005" class="citation book cs1">Matthews, J. (2005). Computer Networking: Internet Protocols in Action (1st ed.). Danvers, MA: John Wiley & Sons Inc.</cite>

</li>

<li id="cite_note-29"><a href="#cite_ref-29">^</a> <cite id="CITEREFSneddon2021" class="citation web cs1">Sneddon, Joey (26 January 2021). <a rel="nofollow" class="external text" href="https://www.omgubuntu.co.uk/2021/01/linux-release-roundup-chrome-lightworks-more">"Linux Release Roundup: GParted, Lightworks, Google Chrome + More"</a>. omgubuntu.co.uk. Retrieved 30 January 2021.</cite>

</li>

<li id="cite_note-30"><a href="#cite_ref-30">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.mozilla.org/en-US/firefox/88.0/releasenotes/">"See what's new in Firefox: 88.0 Firefox Release"</a>. mozilla.org. 19 April 2021. Retrieved 20 April 2021.</cite>

</li>

<li id="cite_note-31"><a href="#cite_ref-31">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20220301212656/https://fireftp.net/">"FireFTP - The Free FTP Client for Waterfox"</a>. FireFTP.net. Archived from <a rel="nofollow" class="external text" href="https://fireftp.net/">the original</a> on 1 March 2022.</cite>

</li>

<li id="cite_note-32"><a href="#cite_ref-32">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://lynx.invisible-island.net/lynx_help/lynx_url_support.html">"URL Schemes Supported in Lynx"</a>. Lynx website. Retrieved 6 July 2023.</cite>

</li>

<li id="cite_note-33"><a href="#cite_ref-33">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://support.mozilla.org/en-US/kb/Accessing%20FTP%20servers#w_ftp-servers-that-require-a-username-and-password">"Accessing FTP servers | How to | Firefox Help"</a>. Support.mozilla.com. 5 September 2012. Retrieved 16 January 2013.</cite>

</li>

<li id="cite_note-34"><a href="#cite_ref-34">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20150702005840/https://support.microsoft.com/en-us/kb/135975">"How to Enter FTP Site Password in Internet Explorer"</a>. Archived from <a rel="nofollow" class="external text" href="https://support.microsoft.com/en-us/kb/135975">the original</a> on 2 July 2015. Retrieved 13 February 2020.</cite> Written for IE versions 6 and earlier. Might work with newer versions.

</li>

<li id="cite_note-35"><a href="#cite_ref-35">^</a> <cite id="CITEREFJukka_“Yucca”_Korpela1997" class="citation web cs1">Jukka “Yucca” Korpela (18 September 1997). <a rel="nofollow" class="external text" href="https://jkorpela.fi/ftpurl.html">"FTP URLs"</a>. "IT and communication" (jkorpela.fi). Retrieved 26 January 2020.</cite>

</li>

<li id="cite_note-36"><a href="#cite_ref-36">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.conceiva.com/products/downloadstudio/features.asp">"DownloadStudio - Internet Download Manager And Download Accelerator - Features"</a>. Conceiva. Retrieved 19 October 2021.</cite>

</li>

<li id="cite_note-37"><a href="#cite_ref-37">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://wiki.documentfoundation.org/ReleaseNotes/7.4">"LibreOffice 7.4: Release Notes"</a>. The Document Foundation's Wiki. Retrieved 10 September 2022.</cite>

</li>

<li id="cite_note-38"><a href="#cite_ref-38">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://wiki.documentfoundation.org/ReleaseNotes/24.2">"ReleaseNotes/24.2"</a>. The Document Foundation's Wiki. Retrieved 24 March 2024.</cite>

</li>

<li id="cite_note-39"><a href="#cite_ref-39">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://wiki.openoffice.org/wiki/Documentation/DevGuide/AppendixC/The_FTP_Content_Provider">"The FTP Content Provider"</a>. Apache OpenOffice Wiki. Retrieved 23 July 2025.</cite>

</li>

<li id="cite_note-40"><a href="#cite_ref-40">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://wiki.openoffice.org/wiki/Documentation/DevGuide/OfficeDev/Path_Settings">"Path Settings"</a>. Apache OpenOffice Wiki. Retrieved 23 July 2025.</cite>

</li>

<li id="cite_note-41"><a href="#cite_ref-41">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://wiki.openoffice.org/wiki/API/Samples/Java/Office/DocumentHandling">"API/Samples/Java/Office/DocumentHandling"</a>. Apache OpenOffice Wiki. Retrieved 23 July 2025.</cite>

</li>

<li id="cite_note-nurdle-42">^ <a href="#cite_ref-nurdle_42-0">a</a> <a href="#cite_ref-nurdle_42-1">b</a> <a href="#cite_ref-nurdle_42-2">c</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://nurdletech.com/linux-notes/ftp/ssh.html">"Securing FTP using SSH"</a>. Nurdletech.com.</cite>

</li>

<li id="cite_note-43"><a href="#cite_ref-43">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20200731160323/https://www.ssh.com/manuals/mft-events-product/63/ssh-solutions-your-business-components.html">"Components of the Information Assurance Platform (section Tectia ConnectSecure)"</a>. ssh.com. Archived from <a rel="nofollow" class="external text" href="https://www.ssh.com/manuals/mft-events-product/63/ssh-solutions-your-business-components.html">the original</a> on 31 July 2020.</cite>

</li>

</ol></div></div>

<div class="mw-heading mw-heading2"><h2 id="Further_reading">Further reading</h2></div>

<ul><li><a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc697">697</a> – CWD Command of FTP. July 1975.</li>

<li><a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc959">959</a> – (Standard) File Transfer Protocol (FTP). J. Postel, J. Reynolds. October 1985.</li>

<li><a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1579">1579</a> – (Informational) Firewall-Friendly FTP. February 1994.</li>

<li><a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1635">1635</a> – (Informational) How to Use Anonymous FTP. May 1994.</li>

<li><a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1639">1639</a> – FTP Operation Over Big Address Records (FOOBAR). June 1994.</li>

<li><a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc1738">1738</a> – Uniform Resource Locators (URL). December 1994.</li>

<li><a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc2228">2228</a> – (Proposed Standard) FTP Security Extensions. October 1997.</li>

<li><a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc2389">2389</a> – (Proposed Standard) Feature negotiation mechanism for the File Transfer Protocol. August 1998.</li>

<li><a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc2428">2428</a> – (Proposed Standard) Extensions for IPv6, NAT, and Extended passive mode. September 1998.</li>

<li><a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc2577">2577</a> – (Informational) FTP Security Considerations. May 1999.</li>

<li><a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc2640">2640</a> – (Proposed Standard) Internationalization of the File Transfer Protocol. July 1999.</li>

<li><a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc3659">3659</a> – (Proposed Standard) Extensions to FTP. P. Hethmon. March 2007.</li>

<li><a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc5797">5797</a> – (Proposed Standard) FTP Command and Extension Registry. March 2010.</li>

<li><a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc7151">7151</a> – (Proposed Standard) File Transfer Protocol HOST Command for Virtual Hosts. March 2014.</li>

<li><a rel="nofollow" class="external text" href="https://www.iana.org/assignments/ftp-commands-extensions/ftp-commands-extensions.xhtml">IANA FTP Commands and Extensions registry</a> – The official registry of FTP Commands and Extensions</li></ul>

<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>

<ul><li> <a href="https://en.wikibooks.org/wiki/Communication_Networks/File_Transfer_Protocol" class="extiw external" title="wikibooks:Communication Networks/File Transfer Protocol">Communication Networks/File Transfer Protocol</a> at Wikibooks</li>

<li><a rel="nofollow" class="external text" href="https://servertest.online/ftp">FTP Server Online Tester</a> Authentication, encryption, mode and connectivity.</li>

<li>Anonymous FTP Servers by Country Code <a href="Top-level_domain" title="Top-level domain">TLD</a> (2012): <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20230328113445/https://www.jumpjet.info/Offbeat-Internet/Public/FTP/url.htm">"Offbeat Internet - Public Access - FTP"</a>. www.jumpjet.info. 2012. Archived from <a rel="nofollow" class="external text" href="https://www.jumpjet.info/Offbeat-Internet/Public/FTP/url.htm">the original</a> on 28 March 2023. Retrieved 16 January 2020.</cite></li></ul>

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbox{box-sizing:border-box;border:1px solid #a2a9b1;width:100%;clear:both;font-size:88%;text-align:center;padding:1px;margin:1em auto 0}.mw-parser-output .navbox .navbox{margin-top:0}.mw-parser-output .navbox+.navbox,.mw-parser-output .navbox+.navbox-styles+.navbox{margin-top:-1px}.mw-parser-output .navbox-inner,.mw-parser-output .navbox-subgroup{width:100%}.mw-parser-output .navbox-group,.mw-parser-output .navbox-title,.mw-parser-output .navbox-abovebelow{padding:0.25em 1em;line-height:1.5em;text-align:center}.mw-parser-output .navbox-group{white-space:nowrap;text-align:right}.mw-parser-output .navbox,.mw-parser-output .navbox-subgroup{background-color:#fdfdfd}.mw-parser-output .navbox-list{line-height:1.5em;border-color:#fdfdfd}.mw-parser-output .navbox-list-with-group{text-align:left;border-left-width:2px;border-left-style:solid}.mw-parser-output tr+tr>.navbox-abovebelow,.mw-parser-output tr+tr>.navbox-group,.mw-parser-output tr+tr>.navbox-image,.mw-parser-output tr+tr>.navbox-list{border-top:2px solid #fdfdfd}.mw-parser-output .navbox-title{background-color:#ccf}.mw-parser-output .navbox-abovebelow,.mw-parser-output .navbox-group,.mw-parser-output .navbox-subgroup .navbox-title{background-color:#ddf}.mw-parser-output .navbox-subgroup .navbox-group,.mw-parser-output .navbox-subgroup .navbox-abovebelow{background-color:#e6e6ff}.mw-parser-output .navbox-even{background-color:#f7f7f7}.mw-parser-output .navbox-odd{background-color:transparent}.mw-parser-output .navbox .hlist td dl,.mw-parser-output .navbox .hlist td ol,.mw-parser-output .navbox .hlist td ul,.mw-parser-output .navbox td.hlist dl,.mw-parser-output .navbox td.hlist ol,.mw-parser-output .navbox td.hlist ul{padding:0.125em 0}.mw-parser-output .navbox .navbar{display:block;font-size:100%}.mw-parser-output .navbox-title .navbar{float:left;text-align:left;margin-right:0.5em}body.skin--responsive .mw-parser-output .navbox-image img{max-width:none!important}@media print{body.ns-0 .mw-parser-output .navbox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style></div><div role="navigation" class="navbox" aria-labelledby="Uniform_Resource_Identifier_(URI)_schemes138" style="padding:3px"><table class="nowraplinks mw-collapsible autocollapse navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><div id="Uniform_Resource_Identifier_(URI)_schemes138" style="font-size:114%;margin:0 4em"><a href="List_of_URI_schemes" title="List of URI schemes">Uniform Resource Identifier (URI) schemes</a></div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%">Official</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="About_URI_scheme" title="About URI scheme">about</a></li>

<li><a href="Gopher_(protocol)" title="Gopher (protocol)">gopher</a></li>

<li><a href="HTTPS" title="HTTPS">https</a></li>

<li><a href="Mailto" title="Mailto">mailto</a></li>

<li><a href="Telnet" title="Telnet">telnet</a></li>

<li><a href="View-source_URI_scheme" title="View-source URI scheme">view-source</a></li>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Unofficial</th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Hyper_Text_Coffee_Pot_Control_Protocol#Commands_and_replies" title="Hyper Text Coffee Pot Control Protocol">coffee</a></li>

<li><a href="Gemini_(protocol)" title="Gemini (protocol)">gemini</a></li>

<li><a href="Finger_(protocol)" title="Finger (protocol)">finger</a></li>

<li><a href="Lightweight_Directory_Access_Protocol#URI_scheme" title="Lightweight Directory Access Protocol">ldaps</a></li>

<li><a href="Magnet_URI_scheme" title="Magnet URI scheme">magnet</a></li>

<li><a href="Rsync" title="Rsync">rsync</a></li>

<li><a href="Yahoo!_Messenger" class="mw-redirect" title="Yahoo! Messenger">ymsgr</a></li></ul>

</div></td></tr><tr><td class="navbox-abovebelow" colspan="2"><div><a href="List_of_network_protocols_(OSI_model)" title="List of network protocols (OSI model)">Protocol list</a></div></td></tr></tbody></table></div>

<div class="navbox-styles"></div><div role="navigation" class="navbox authority-control" aria-labelledby="Authority_control_databases_frameless&#124;text-top&#124;10px&#124;alt=Edit_this_at_Wikidata&#124;link=https&#58;//www.wikidata.org/wiki/Q42283#identifiers&#124;class=noprint&#124;Edit_this_at_Wikidata718" style="padding:3px"><table class="nowraplinks hlist mw-collapsible autocollapse navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><div id="Authority_control_databases_frameless&#124;text-top&#124;10px&#124;alt=Edit_this_at_Wikidata&#124;link=https&#58;//www.wikidata.org/wiki/Q42283#identifiers&#124;class=noprint&#124;Edit_this_at_Wikidata718" style="font-size:114%;margin:0 4em">Authority control databases </div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%">National</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"><ul><li><a rel="nofollow" class="external text" href="https://d-nb.info/gnd/4268371-3">Germany</a></li><li><a rel="nofollow" class="external text" href="https://id.loc.gov/authorities/sh95000465">United States</a></li><li><a rel="nofollow" class="external text" href="https://www.nli.org.il/en/authorities/987007530226005171">Israel</a></li></ul></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Other</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"><ul><li><a rel="nofollow" class="external text" href="https://lux.collections.yale.edu/view/concept/094489ea-34e0-40c4-8911-c87bb7254495">Yale LUX</a></li></ul></div></td></tr></tbody></table></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-07-23" href="https://en.wikipedia.org/wiki/?title=File_Transfer_Protocol&oldid=1302133829">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>